-
-
Notifications
You must be signed in to change notification settings - Fork 760
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable Gradle's configuration cache by default #4576
Conversation
I've updated the label to "housekeeping" since I thought the yellow labels, including "gradle", related to the named subprojects? This doesn't change behaviour of the detekt Gradle plugin at all, just the detekt build itself. Happy to switch back though if that makes sense when it comes to generating release notes. |
Codecov Report
@@ Coverage Diff @@
## main #4576 +/- ##
=========================================
Coverage 84.45% 84.45%
Complexity 3330 3330
=========================================
Files 479 479
Lines 11143 11143
Branches 2040 2040
=========================================
Hits 9411 9411
Misses 699 699
Partials 1033 1033 Continue to review full report at Codecov.
|
Yup that's better. I've initially added |
* Flag tasks known to be incompatible with Gradle's configuration cache * Enable Gradle's configuration cache by default
Gradle 7.4 introduces a feature to declare that individual tasks are incompatible with the configuration cache, allowing the feature to be enabled by default while skipping caching when there are tasks in the task graph that don't support it.
More information available in "Disable configuration caching when incompatible tasks are executed" section of the release notes: https://docs.gradle.org/7.4/release-notes.html#config-cache
This PR enables the configuration cache while declaring tasks known to be incompatible with it. Note that there may be some additional tasks that are discovered to be incompatible in future, so this config might need tweaking.